ESOK-hanke 2006-2011

Foxability - Test results

Test results

Test results

Test subject: https://testikorppi.avoin.it.jyu.fi/kotka/portal/addOuUser/step1.jsp

Statistics for the evaluated page

Total tests: 47

TestsPercentTotalPercent
Total passed:3676.60%3628.57%
-Passed with remarks:1634.04%2116.67%
Failed:1021.28%6450.79%
Warnings:12.13%53.97%
Total:47100.00%126100.00%

WCAG 1.0 A

Guideline 1

(show module information)

1.1 - Elements have text equivalents. (6)

(hide test results)
  1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/ajax/jquery-1.2.4a.js" type="text/javascript" language="javascript"></scr .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  2. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/sorttable.js" type="text/javascript" language="javascript"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  3. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/scripts.js" type="text/javascript" language="javascript"></script> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/calendar/miniCalendar/miniCalendar.js" type="text/javascript" language="javascri .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  5. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- var userLanguageId = 2; var PATH_DOCUMENTROOT = '/kotka'; //--> .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
  6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- document.onkeypress = checkSubmissions; function checkSubmissi .
    • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
Test result
Failed

1.2 - A serverside Image map without an alternative textlink

    Test result
    Passed

    1.3 - Auditory descriptions for visual tracks.

    (hide test results)
    1. Remark, until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
    Test result
    Passed

    1.4 - Equivalent alternatives for time based multimedia.

    (hide test results)
    1. Remark, for any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
    Test result
    Passed

    Guideline 2

    (show module information)

    2.1 - Information is conveyed even without colors.

    (hide test results)
    1. Remark, ensure that all information conveyed with color is also available without color, for example from context or markup.
    Test result
    Passed

    Guideline 4

    (show module information)

    4.1 - Language changes are identified.

    (hide test results)
    1. Remark, if multiple languages are used in the document, clearly identify changes in the natural language of the document's text.
      • Use the "lang" or "xml:lang" attribute to identify any changes in language. For example: Galileo said quietly: <q lang="it">Eppur si muove</q>
    Test result
    Passed

    Guideline 5

    (show module information)

    5.1 - Table used properly

      Test result
      Passed

      5.2 - Associate data cells and header cells

      (hide test results)
      1. Remark, for data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-table-structure.
      Test result
      Passed

      Guideline 6

      (show module information)

      6.1 - Organize documents so they may be read without style sheets

      (hide test results)
      1. Remark, 1 deprecated elements were found. Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
        • Ensure this document can be read without any styles or style sheets.
      Test result
      Passed

      6.2 - Ensure that equivalents for dynamic content are updated when thedynamic content changes (6)

      (hide test results)
      1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/ajax/jquery-1.2.4a.js" type="text/javascript" language="javascript"></scr .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      2. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/sorttable.js" type="text/javascript" language="javascript"></script> .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      3. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/scripts.js" type="text/javascript" language="javascript"></script> .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/calendar/miniCalendar/miniCalendar.js" type="text/javascript" language="javascri .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      5. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- var userLanguageId = 2; var PATH_DOCUMENTROOT = '/kotka'; //--> .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- document.onkeypress = checkSubmissions; function checkSubmissi .
        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
      Test result
      Failed

      6.3 - Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported

        Test result
        Passed

        Guideline 7

        (show module information)

        7.1 - Avoid causing the screen to flicker

        (hide test results)
        1. Remark, until user agents allow users to control flickering, avoid causing the screen to flicker. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-flicker.
        Test result
        Passed

        Guideline 8

        (show module information)

        8.1 - Programmatic elements such as scripts and applets must/should be directly accessible or compatible with assistive technologies (6)

        (hide test results)
        1. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script src="/kotka/shared/ajax/jquery-1.2.4a.js" type="text/javascript" language="javascript"></scr .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        2. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script src="/kotka/shared/sorttable.js" type="text/javascript" language="javascript"></script> .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        3. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script src="/kotka/shared/scripts.js" type="text/javascript" language="javascript"></script> .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        4. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script src="/kotka/calendar/miniCalendar/miniCalendar.js" type="text/javascript" language="javascri .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        5. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- var userLanguageId = 2; var PATH_DOCUMENTROOT = '/kotka'; //--> .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        6. Remark, this element may not be accessible to all users. Please ensure there is an accessible interface to this object. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- document.onkeypress = checkSubmissions; function checkSubmissi .
          • Ensure that scripts, applets, or other programmatic objects are directly accessible. More information from http://www.w3.org/TR/AERT#linear-tables.
        Test result
        Passed

        Guideline 9

        (show module information)

        9.1 - Client-side versus server-side image maps

          Test result
          Passed

          Guideline 11

          (show module information)

          11.4 - Accessible page

          (hide test results)
          1. Remark, if, after best efforts, you cannot create an accessible page, provide a link to an alternative page that is accessible, has equivalent information, and is updated as often as the inaccessible page. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-alt-pages.
          Test result
          Passed

          Guideline 12

          (show module information)

          12.1 - Providing a frame title

            Test result
            Passed

            Guideline 14

            (show module information)

            14.1 - Clear and simple language.

            (hide test results)
            1. Remark, use the clearest and simplest language appropriate for a site's content.
            Test result
            Passed

            WCAG 1.0 AA

            Guideline 3

            (show module information)

            3.1 - MathML

              Test result
              Passed

              3.2 - Formal grammars.

                Test result
                Passed

                3.3 - Proper font stylings. (4)

                (hide test results)
                1. Failed, deprecated element found. Error was found from FONT element code: <font color="#c0c0c0">27</font> .
                  • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
                2. Failed, deprecated element found. Error was found from FONT element code: <font color="#c0c0c0">28</font> .
                  • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
                3. Failed, deprecated element found. Error was found from FONT element code: <font color="#c0c0c0">29</font> .
                  • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
                4. Failed, deprecated element found. Error was found from FONT element code: <font color="#c0c0c0">30</font> .
                  • Font stylings should be made with CSS or in element's style attribute. CSS example: p { font: italic 1.5em/2em Palatino, serif; }
                Test result
                Failed

                3.4 - Relative over absolute. (29)

                (hide test results)
                1. Failed, absolute size definition found. .navbar:"padding-top: 5px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                2. Failed, absolute size definition found. .navbar:"height: 65px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                3. Failed, absolute size definition found. .navbar:"width: 240px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                4. Failed, absolute size definition found. .korppi .navbar .exit:"min-height: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                5. Failed, absolute size definition found. .korppi .navbar .exit a:"height: 45px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                6. Failed, absolute size definition found. .korppi .navbar .exit a:"width: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                7. Failed, absolute size definition found. .korppi .navbar .settings:"min-height: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                8. Failed, absolute size definition found. .korppi .navbar .settings a:"height: 45px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                9. Failed, absolute size definition found. .korppi .navbar .settings a:"width: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                10. Failed, absolute size definition found. .korppi .navbar .feedback:"min-height: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                11. Failed, absolute size definition found. .korppi .navbar .feedback a:"height: 45px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                12. Failed, absolute size definition found. .korppi .navbar .feedback a:"width: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                13. Failed, absolute size definition found. .korppi .navbar .help:"min-height: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                14. Failed, absolute size definition found. .korppi .navbar .help a:"height: 45px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                15. Failed, absolute size definition found. .korppi .navbar .help a:"width: 40px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                16. Failed, absolute size definition found. .korppi .logoblock:"height: 70px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                17. Failed, absolute size definition found. .main:"left: 200px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                18. Failed, absolute size definition found. .main:"padding-left: 10px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                19. Failed, absolute size definition found. .main:"top: 75px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                20. Failed, absolute size definition found. .korppi .logoblock:"height: 70px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                21. Failed, absolute size definition found. .uppernavbar:"left: 220px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                22. Failed, absolute size definition found. .navbar:"width: 300px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                23. Failed, absolute size definition found. .navbarimage:"width: 70px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                24. Failed, absolute size definition found. .leftbar:"width: 220px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                25. Failed, absolute size definition found. .main:"left: 230px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                26. Failed, absolute size definition found. .main:"padding-left: 10px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                27. Failed, absolute size definition found. .main:"top: 80px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                28. Failed, absolute size definition found. .breadcrumb:"margin-left: -25px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                29. Failed, absolute size definition found. .breadcrumb:"margin-top: -10px". Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                  • Use relative size definitions. Relative size definitions are: em, ex and %. For example: "margin-left: 2%"
                Test result
                Failed

                3.5 - Proper header usage.

                (hide test results)
                1. Failed, improper header nesting: Header levels must not increase by more than one level per heading. Do not use headers to create font effects; use style sheets to change font styles. Error was found from H3 element code: <h3>Muut tiedot</h3> .
                  • Lower the header level to at least <h2>.
                Test result
                Failed

                3.6 - Proper List usage.

                  Test result
                  Passed

                  3.7 - Proper quote usage.

                    Test result
                    Passed

                    Guideline 5

                    (show module information)

                    5.3 - Table is used as layout

                      Test result
                      Passed

                      Guideline 6

                      (show module information)

                      6.1 - Organize documents so they may be read without style sheets

                      (hide test results)
                      1. Remark, 1 deprecated elements were found. Error was found from LINK element code: <link href="/kotka/styles/korppiWeb20_blue.css" title="Korppi-tyylitiedosto" rel="stylesheet" type=" .
                        • Ensure this document can be read without any styles or style sheets.
                      Test result
                      Passed

                      6.2 - Ensure that equivalents for dynamic content are updated when thedynamic content changes (6)

                      (hide test results)
                      1. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/ajax/jquery-1.2.4a.js" type="text/javascript" language="javascript"></scr .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      2. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/sorttable.js" type="text/javascript" language="javascript"></script> .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      3. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/shared/scripts.js" type="text/javascript" language="javascript"></script> .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      4. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script src="/kotka/calendar/miniCalendar/miniCalendar.js" type="text/javascript" language="javascri .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      5. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- var userLanguageId = 2; var PATH_DOCUMENTROOT = '/kotka'; //--> .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      6. Failed, <noscript> after <script> not found. Error was found from SCRIPT element code: <script type="text/javascript"> <!-- document.onkeypress = checkSubmissions; function checkSubmissi .
                        • Insert <noscript> after <script>. For example: <script>...</script><noscript>A graph about oil price.</noscript>
                      Test result
                      Failed

                      6.3 - Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported

                        Test result
                        Passed

                        6.4 - For scripts and applets, ensure that event handlers are input device-independent

                          Test result
                          Passed

                          6.5 - Ensure that dynamic content is accessible or provide an alternative presentation or page

                            Test result
                            Passed

                            Guideline 7

                            (show module information)

                            7.2 - Blink and marquee usage

                              Test result
                              Passed

                              7.3 - Avoid movement in page

                              (hide test results)
                              1. Remark, until user agents allow users to freeze moving content, avoid movement in pages. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-movement.
                              Test result
                              Passed

                              7.4 - Periodically auto-refreshing pages

                                Test result
                                Passed

                                7.5 - Autoredirection

                                  Test result
                                  Passed

                                  Guideline 9

                                  (show module information)

                                  9.2 - Ensuring any element with own interface to be operated in a device-independent manner

                                    Test result
                                    Passed

                                    9.3 - Logical event handlers are specified for scripts, rather than device-dependent event handlers

                                      Test result
                                      Passed

                                      Guideline 10

                                      (show module information)

                                      10.1 - No pop-ups or other windows

                                        Test result
                                        Passed

                                        10.2 - The properly positioned label considering all form controls with implicitly associated labels (2)

                                        (hide test results)
                                        1. Failed, wrong label usage. Error was found from INPUT element code: <input name="studyPurpose_other" size="30" value="" type="text"> .
                                          • Use label right before or after input and use for - id relationship or parentship.More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels.
                                        2. Failed, wrong label usage. Error was found from INPUT element code: <input name="howGotInfo_other" size="30" value="" type="text"> .
                                          • Use label right before or after input and use for - id relationship or parentship.More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-unassociated-labels.
                                        Test result
                                        Failed

                                        Guideline 11

                                        (show module information)

                                        11.1 - Use of W3C technologies

                                        (hide test results)
                                        1. Remark, use W3C technologies when they are available and appropriate for a task and use the latest versions when supported More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-latest-w3c-specs.
                                        Test result
                                        Passed

                                        11.2 - Avoid using deprecated features of W3C technologies. (4)

                                        (hide test results)
                                        1. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#c0c0c0">27</font> .
                                          • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                        2. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#c0c0c0">28</font> .
                                          • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                        3. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#c0c0c0">29</font> .
                                          • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                        4. Failed, this HTML element is now deprecated and should not be used. Error was found from FONT element code: <font color="#c0c0c0">30</font> .
                                          • Find all about deprecated elements from http://www.w3.org/TR/WCAG10-TECHS/#tech-avoid-deprecated.
                                        Test result
                                        Failed

                                        Guideline 12

                                        (show module information)

                                        12.2 - Describe the purpose of frames

                                        (hide test results)
                                        1. Remark, describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-frame-longdesc.
                                        Test result
                                        Passed

                                        12.3 - Dividing large blocks of information into more manageable groups (5)

                                        (hide test results)
                                        1. Failed, Improper header nesting: Header levels must not increase by more than one level per heading. Do not use headers to create font effects; use style sheets to change font styles. Error was found from H3 element code: <h3>Muut tiedot</h3> .
                                          • Lower the header level to at least <h2>.
                                        2. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="miniCalendar"><tbody><tr><th class="arrowLeft actionImg"></th><th colspan="6" class="c .
                                          • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                        3. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="backgroundinfo"> <caption>Opintojesi tarkoitus</caption><tbody><tr> <td><input id="stu .
                                          • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                        4. Failed, use in table at least two of next three: caption, summary and title. Error was found from TABLE element code: <table class="backgroundinfo"> <caption>Mistä sait tietää opinnoista?</caption><tbody><tr> <td><inpu .
                                          • Use in table at least two of next three: caption, summary and title. Caption is element of table. Summary and title are attributes of table. Example: <table title="Calendar" summary="This is christmosh calendar. Shows how many days is left before Christmosh."> <caption>Christmosh calendar</caption>... More information from http://www.w3.org/TR/AERT#table-summaries.
                                        5. Warning, there are too many (20 or more) input in form that are not grouped. Error was found from FORM element code: <form id="wizardform" action="step1.jsp" method="post"> <div class="toiminta marg_top_1"> <div .
                                          • Group input-elements by fieldset-element to logic and semantic groups that are easy to understand. More from http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-grouping.
                                        Test result
                                        Failed

                                        12.4 - Associating labels explicitly with their controls (2)

                                        (hide test results)
                                        1. Failed, input does not have label. Error was found from INPUT element code: <input name="studyPurpose_other" size="30" value="" type="text"> .
                                          • Use label right before or after input and use for - id relationship or parentship.
                                        2. Failed, input does not have label. Error was found from INPUT element code: <input name="howGotInfo_other" size="30" value="" type="text"> .
                                          • Use label right before or after input and use for - id relationship or parentship.
                                        Test result
                                        Failed

                                        Guideline 13

                                        (show module information)

                                        13.1 - Target of each link (4)

                                        (hide test results)
                                        1. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/kotka/calendar/calendar.jsp?type=day&amp;date=27.4.2009"><font color="#c0c0c0">27</font></ .
                                          • Use unique and meaningfull name and title for different links.
                                        2. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/kotka/calendar/calendar.jsp?type=day&amp;date=28.4.2009"><font color="#c0c0c0">28</font></ .
                                          • Use unique and meaningfull name and title for different links.
                                        3. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/kotka/calendar/calendar.jsp?type=day&amp;date=29.4.2009"><font color="#c0c0c0">29</font></ .
                                          • Use unique and meaningfull name and title for different links.
                                        4. Warning, found two identical name and title for two different links. Error was found from A element code: <a href="/kotka/calendar/calendar.jsp?type=day&amp;date=30.4.2009"><font color="#c0c0c0">30</font></ .
                                          • Use unique and meaningfull name and title for different links.
                                        Test result
                                        Warning

                                        13.2 - Metadata should be used to add semantic information to pages and sites

                                          Test result
                                          Passed

                                          13.3 - Information about the general layout

                                          (hide test results)
                                          1. Remark, provide information about the general layout of a site (e.g., a site map or table of contents). More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-site-description.
                                          Test result
                                          Passed

                                          13.4 - Navigation mechanisms

                                          (hide test results)
                                          1. Remark, use navigation mechanisms in a consistent manner. More information from http://www.w3.org/TR/WCAG10-TECHS/#tech-clear-nav-mechanism.
                                          Test result
                                          Passed
                                          kuuluu seuraaviin kategorioihin: , ,